Release 10.1A: OpenEdge Development:
Debugging and Troubleshooting

Debugging from the Procedure Editor

Starting the Debugger from the Procedure Editor runs the Debugger in application mode, ready to debug the procedure that is running and any other procedures you choose.

To start a debugging session from the Procedure Editor, enter or open a procedure in the Editor buffer and choose Compile Debug. Figure 2–3 shows the Procedure Editor in Windows.

Figure 2–3: Debugging from the Procedure Editor

After you choose Compile Debug, the Procedure Editor:

Saves a temporary file containing your procedure to the current working directory, using a unique, alphanumeric filename with a .ped extension (as the Procedure Editor always does).
Initializes the Debugger.
Sets a breakpoint on the first executable line of your procedure.
Runs your procedure.

The 4GL interpreter immediately gives control to the Debugger at the initial breakpoint.